Device Assisted Multi-Step Adaptive Discontinuous Reception (DRX) Operations Using Power Preference Indicator

ABSTRACT

Examples of power conservation management for user equipment based on the operating state of the user equipment are provided. A user equipment may implement a power managing application that monitors the activity of the user equipment, such as the number of applications open on the user equipment, the data usage requirements for each open application, data delay tolerances for each application and/or a level of user interaction with the device at a given moment. Based on the level of activity and the data requirements, the managing application on the user equipment is able to make a discontinuous reception profile setting recommendation selected from more than two discontinuous reception profiles to the mobile communications network entity. In response to the discontinuous reception profile setting recommendation, the network entity may modify the connection status with the user equipment.

BACKGROUND

In recent years, an area of intensive research has been in theconservation of battery life of a mobile device. As a greater number ofapplications are becoming available that require near constant networkaccess and require power on a near constant basis, the previous methodsof conserving power on a mobile device are not compatible with today'strend of increased data and power usage.

One of the issues is a frequent use of network assets as the mobiledevices disconnect from the network and then attempt to reconnect aftera short amount of time. The connection/reconnection attempts consumesignaling bandwidth, and when a large number of devices are attemptingto access the network, a large amount of the signaling bandwidth isconsumed.

In long term evolution (LTE) networks, discontinous reception (DRX) is apower saving method executed by a mobile device during communicationbetween the mobile device and a cellular communication network to whichthe mobile device is connected. DRX is a setting in the mobile devicethat is set by an entity in the cellular communication network (e.g., aneNodeB) based on a message to a mobile device (i.e., the User equipment(UE) in a mobile network context). The DRX message from the eNodeBinstructs the UE to remain in one of two states: connected or inactive.Said differently, when the UE receives a DRX “connected” message the UEremains active (i.e., stays connected—receiving data from and/ortransmitting data to the network), but when the UE receives the“inactive” DRX message, the UE sleeps (i.e., goes into or remains in aninactive state—remains idle and does not receive or transmit data to thenetwork). The UE follows a protocol defined by the network to switchbetween sleep and active modes. The longer the sleeping period andshorter the active periods, the greater the power savings.

However, there is a trade off between data throughput and power saving.From a power saving point of view, a UE needs to more frequently enterinto the sleep mode to save power. But to send or receive data, the UEthen has to transition back to the active state. Transition to an activestate includes signaling the network. Depending on the traffic patterns,the UE may frequently transition between sleep mode and active mode,which may result in high volume of network signalling and/or datathroughput jitter. Jitter may be defined as arrival time variations ofvoice-over-IP (VoIP) packets due to network congestion, timing drift,and/or route changes. From the throughput point of view, the UE shouldalways be active in order to achieve the best data throughput results.It is very difficult to achieve a balance between power savings andthroughput.

Typically, an eNodeB of a cellular communication network provides DRXsetting instructions to an UE. Based on the DRX setting instructions,the UE sets its DRX setting. For example, the eNodeB will set one DRXsetting for VoIP, while data communication will have another DRXsetting. Currently, the eNodeB has complete control of the DRX settingsfor a UE, and the UE has no input into the DRX setting. The DRX settinginstructions sent by an eNodeB may not conform to the current use of theUE.

However, in a latest standard release, 3GPP standard, Release 11, a UEcan send a signal to an eNodeB of cellular communicaiton network thatinfluences the network configuration. The signal sent by the UE is aPower Preference Indicator (PPI), which is a single bit value (i.e., 0or 1) indication defined by 3GPP standard, Release 11.

It has been suggested to use the PPI signal to select between a lowlatency DRX profile (PPI=0) (e.g., remains active for longer periods butsleeps less) and a low power DRX profile (PPI=1) (e.g., sleeps moreoften or for longer periods but is less active). However, thissuggestion allows only two possible profiles since the PPI is a singlebit definition state indicator. Due to different types of data trafficand UE data usage scenarios, there is a need to have more flexible waysto specify and control more than two DRX profiles so a better balancebetween power and throughput may be achieved.

BRIEF DESCRIPTION OF THE DRAWINGS

The drawing figures depict one or more implementations in accord withthe present teachings, by way of example only, not by way of limitation.In the figures, like reference numerals refer to the same or similarelements.

FIG. 1 is a high-level functional block diagram of an example of asystem of networks/devices that provide various communications formobile devices and support an example of the UE DRX profile selectionservice.

FIG. 2 illustrates a high-level functional block diagram of a PowerPreference Indicator management application of a UE and a communicationnetwork entity components supporting the selection of a DRX profilesetting for the UE.

FIG. 3 is a call flow diagram of an example scenario for updating a DRXprofile setting based on changes in the operating status of a UE.

FIG. 4 is an example of a data structure used in the adaptive DRXprofile setting service.

FIG. 5 is a high-level functional block diagram of an example of touchscreen type mobile station as may utilize the adaptive DRX profilesetting service through a network/system like that shown in FIG. 1.

FIG. 6 is a simplified functional block diagram of a wireless networknode, such as an evolved node B (eNodeB) found in the system of FIG. 1and described in FIGS. 2 and 3.

FIG. 7 is a simplified functional block diagram of a computer that maybe configured as a host or server, for example, to function as a DRXprofile server in the system of FIG. 1.

DETAILED DESCRIPTION OF EXAMPLES

In the following detailed description, numerous specific details are setforth by way of examples in order to provide a thorough understanding ofthe relevant teachings. However, it should be apparent that the presentteachings may be practiced without such details. In other instances,well known methods, procedures, components, and/or circuitry have beendescribed at a relatively high-level, without detail, in order to avoidunnecessarily obscuring aspects of the present teachings.

The various examples disclosed herein relate to selecting differentnetwork power conservation levels for a UE based on the operating stateof the UE. For example, a power managing application executing on themobile device monitors the activity of the UE, such as the number ofapplications operating (e.g., including background applications) on theUE, the data usage requirements for each operating application, datadelay tolerances for each application and a level of user interactionwith the device at a given moment (i.e., input and output device usage),and other information. Based on the monitored level of activity and thedata requirements, the managing application on the UE is able to make aDRX profile recommendation to the mobile communications network entity,in this example, an eNodeB. In response to the DRX recommendation, theeNodeB may modify the connection status of the UE. However, the DRXprofile recommendation is not based on a choice between only two DRXprofiles as discussed above, but between more than two DRX profiles.Other examples, as explained in more detail below, describe an adaptiveDRX profile recommendation provided to a server connected to the eNodeB.In response to the recommendation, the server provides a DRX profilemodification to the eNodeB, which is forwarded to the UE.

The connection status of the UE is selected from, not just two DRXprofiles, but from some greater number (i.e., greater than 2) ofdifferent DRX profiles. Each profile may be a combination of differentconnected (i.e., active) and inactive (e.g., sleep or idle) periods thatare optimized (as much as possible) for the different system operatingstates of the UE. An operating state may be defined by the number ofapplications executing on a UE, the type of applications executing onthe UE, the data requirements of the executing applications, the datadelay tolerances of the executing applications, and other parametersrelated to the executing applications, the UE system (e.g.,encoder/decoder (video and audio)) performance capabilities, the qualityof service (QoS) parameters for the UE connection with the mobilecommunications network, and the like.

The various system, mobile device and method examples discussed in thissection relate to a service that provides a capability to manage powerconservation settings via use of more than two (>2) DRX profiles for aDRX-enabled mobile device. In an example, the described system, methodand DRX-enabled mobile device utilize non-Session InitiationProtocol-based communications over an Internet connection to provide theservice that provides a capability to manage power conservation settingsvia use of more than two (>2) DRX profiles. In another example, thedescribed system, method and DRX-enabled mobile device utilize an IPMultimedia Subsystem or an IP Multimedia Core Network Subsystem (IMS) toimplement the service that provides a capability to manage powerconservation settings via use of more than two (>2) DRX profiles. IMS isan architectural framework for delivering Internet Protocol (IP)multimedia services. IMS uses the Session Initiation Protocol (SIP) toprovide integration with the Internet, and provides access of multimediaand voice applications from wireless and wireline terminals. A user canconnect to IMS in different ways, including the standard InternetProtocol (IP). IMS terminals or UEs (e.g., mobile phones, computers, andpersonal digital assistants (PDAs)) can register directly on IMS, evenwhen they are roaming in a different network, as long as IP and SIP areaccessible. Mobile access via an LTE mobile network, other wirelessaccess (e.g., Wi-Fi, WLAN, WiMAX), and fixed access (e.g., cable modems,Ethernet, DSL) are all supported.

A communication signaling protocol, for example, hypertext transportprotocol (HTTP), simple mail transport protocol (STMP), real-timetransport protocol (RTP) and session initiation protocol (SIP) is usedin the establishment and control of sessions between multiple users thatenable the multiple users to communicate with each other and withvarious network devices. The described examples may be used with anynumber of signaling communication protocols with messages thatestablish, terminate and perform other functions related to dataexchanges (including voice) between devices. SIP is a signaling protocolutilized in IMS networks, for example, for set-up of sessions for voiceor video calls as well as a variety of other data services. Shown inFIG. 1 are various pathways for signaling messages that are sent backand forth between the end users and various hardware devices within theIMS networks, in this example, to set up a mobile device-to-mobiledevice call. A general description of these components and the signalingbetween these components will now follow, after which examples of callflows will be described in somewhat more detail.

FIG. 1 shows a system 100 and signaling flow for a mobile communicationsession between a user equipment (UE) 105 and another device or system,such as a data server or another UE. In general, UE 105 communicate withtheir respective wireless access network 101 that have a connection to acore network 102 that connect to other networks to provide signaling toestablish voice and data connections with destination or recipientdevices/systems.

The wireless access network 101, for example, may include cellularand/or Wi-Fi network, and the core network 102 may be packet datanetwork (PDN) or an evolved packet core (EPC). The wireless accessnetwork 101 may be accessed via base stations, such as an eNodeB 112 (orthe like). One or more of wireless access network 101 might beimplemented as a network conforming to the long term evolution (LTE)standard, or a Wi-Fi network according to 802.11xx or the like. Accessto the Wi-Fi network of wireless access network 101 may be via awireless access point (WAP) 103. The core network 102 may provideservices such as a home subscriber server (HSS) 114, and a packet datagateway (PGW) 111. The HSS 114 may provide subscriber informationrelated to the access to the respective networks 101, 102, and 110. Theother network elements, such as data servers 157, may further facilitatesession setup and provision of multimedia services to the UE 105.

The communications in a communication signaling protocol from each ofthe respective wireless access network 101 and core network 102 arepassed to the respective IMS network 110 through packet data networkgateway (PGW) device 111. The PGW 111 acts as an interface between, forexample, the core network 102 and IMS network 110. Also included in IMScore 110 are one or more servers, called call session control function(CSCF) servers that control the signaling between the UE 105 via the IMSnetwork 110 to set-up a communication session with a destination UE or adata server. The initial contact by a UE 105 with the network 110 isthrough a proxy call session control function (P-CSCF) server 116 thatacts as a SIP proxy server for network 110 and receives control signalsfrom devices external to the network 110, such as the UE 105. A servingcall session control function (S-CSCF) server 117 acts as a point ofcontrol in the network 110 and provides a number of functions to controlthe sessions between the mobile devices. For example, the S-CSCF server117 authenticates mobile devices with the network 110 communicates withthe charging functions to insure an mobile device has proper permissionsto access network services; serves to translate telephone numbers ofmobile devices to uniform resource identifiers (URI) for use in thenetwork 110; keeps track of charges incurred by users when access dataservices (e.g., data delivered to/from one or more of data servers 157;and other services.

The P-CSCF server 116 may serve as a first point of contact between acalling mobile device 101 and IMS core 110. The P-CSCF server 116 mayserve as an outbound/inbound SIP proxy server, where requests initiatedby the calling mobile device 105, may traverse the P-CSCF server 116.For example, when attempting to establish a call session using acommunication signaling protocol, such as SIP, the P-CSCF server 116 istypically the first point of contact in the IMS network, such as IMScore 110 that receives, for example, a voice over packet protocolmessage (e.g., a SIP INVITE message). The P-CSCF server 116 thenutilizes the S-CSCF server 117 to locate the S-CSCF server 117 in thedestination devices network (not shown).

The S-CSCF server 117 may include a communication signaling protocol(e.g., SIP) server that serves as a central node in the communicationsignaling protocol signaling plane. The S-CSCF server 117 may performsession control. Another network element incorporated into the P-CSCFserver 116 may be an interrogating call session control function(I-CSCF) server (not shown), which may include a communication signalingprotocol server that may be located at an edge of an administrativedomain. The I-CSCF server 116 may publish its IP address in the DomainName System (DNS) record of the domain in which the I-CSCF server 116resides so that remote servers can find the I-CSCF server 116 and usethe I-CSCF server 116 as a forwarding point for communication signalingprotocol packets in the domain. In addition to communication signalingprotocol proxy functionality, the I-CSCF server 116 may include aninterface to the HSS (114) to retrieve user information and to routemessages to an appropriate destination (e.g., S-CSCF server 117) or dataserver 157.

Another network element may be a communication signaling protocoltelephony application server (TAS) 119 that provides applications foruse by a mobile device. The TAS 119 provides services throughapplications related to signaling and media distribution. For example,signaling refers to resolving routing related to free calls, resolvingtelephone number translations that allow for telephone numberportability and the like, while media distribution refers toestablishing voice and video calling, conference calling and similarservices. Yet another network element is a media resource function (MRF)device 113 that is configured to control the establishment/charging ofresources within IMS core 110. The communication signaling protocol TAS119 may include a communication signaling protocol entity that hosts andexecutes services, and interfaces with the S-CSCF server 117. The HSS114 may include a master user database that supports IMS network 110 andcontains subscription-related information. The HSS 114 may performauthentication and authorization of users and can provide informationabout a subscriber's location and IP information. As a call requestmessage generated by a calling party is transmitted from one networkelement to another network element for subsequent delivery to adestination party (including one or more of data servers 157), the callrequest message may be updated by the respective network element toinclude a custom header. The custom header may include information thatidentifies the respective network element, provides instructions for asubsequent network element, causes the respective network element totake an action based on the information, or the like. For ease ofexplanation and discussion, the call request will be referred to interms of SIP messages. For example, a call request message in the SIPprotocol, a SIP INVITE message, may have a custom header directed toanother device or service in the network that receives SIP messages.

Networks 110 may include any type of network or combination of networkssuch as LAN, WLAN, WAN, WWAN, etc. The network 110 may be capable ofproviding a variety of communication network services, such asregistration services, authentication services, authorization services,call session control services and other types of communication services.Specifically, these networks may be configured to include IMS networks.The network 110 may communicate with one another through various networkcomponents.

The LTE standard includes protocols, such as a Radio Resource Control(RRC) protocol, which is responsible for the assignment, configuration,and release of radio resources between a user equipment (e.g., a mobiletelephone, a smartphone, mobile devices, and the like) and a basestation, such as an eNodeB, other access point equipment or LTEequipment. According to the RRC protocol, the two basic RRC modes forthe UE are a “connected mode” and an “idle mode.” During the idle mode,the user device may shut down at least some of its connected modeoperations. During the connected mode, the user device may exchangesignals with a network and may perform other related operations. Whilein the “connected mode” the UE 105 may have multiple DRX profilesavailable for consideration to respond to decreasing power consumptionstates. The transitions to the lower power consuming states are based ontimers referred to as inactivity timers. From time to time, the eNodeBmay send signals to the respective UE indicating that the RRC connectionmode is being reconfigured. The described examples describe theselection of an appropriately suited DRX profile for the presentoperating state of the UE from a multitude (more than two) of variousDRX profiles to more effectively manage the power settings of a UE.

Current 3GPP Release 11 allows for a single bit value (i.e., 1 or 0) tobe used for switching between the two DRX settings described in Release11. In Release 11, the network, such as via the eNodeB 112, 512,dictates which of the two DRX setting the UE is to be set. In contrast,the described examples extend the use of a single bit PPI by providingexamples of a dynamic method in which a UE recommends a selection of oneoptimum profile from multiple (more than 2) DRX profiles using thesingle 3GPP PPI bit signal. As will be described in more detail later,the single PPI bit signal is used to indicate direction within a DRXprofile data structure and the number of transmissions of the PPI signalwithin a time period indicating the number of steps from one DRX profileto a next DRX profile within the DRX profile data structure. Based onthe bit value and number of PPI signals, the DRX profile settings areselected for communication between the respective UE 105 and any eNodeBssuch as 112.

In order to facilitate the use of the multiple DRX profiles andgeneration of the correct number and bit value PPI signals, therespective UE 105 may include a Power Preference Indicator (PPI) managerapplication. The PPI manager application is configured to monitor theoperational state of the UE 105 and exchange information with anappropriately programmed eNodeB, such as 112. The appropriatelyprogrammed eNodeB is configured to execute program instructions thatallow the eNodeB 112 to receive from the UE 105 the single PPI bitsignals and make the appropriate change to the DRX profile. In anexample for providing DRX profile setting assistance to the eNodeB 112,a DRX profile server 131 may be in communication with the eNodeB 112 andprovide information related to the DRX profiles that are optimum for thecurrent communication session between the UE 105 and the eNodeB 112. Forexample, the eNodeB 112 may transmit to the DRX profile server 131 arequest that includes information (e.g., the mobile device number (MDN))that is used to identify a discontinuous reception profile tableassociated with the UE 105. The DRX profile server 131 is configured torespond to the request by sending to the eNodeB 112 a DRX profilesetting table associated with the UE 105, a current DRX profile settingfor the UE 105 based on the request information, or the like based onthe request information. Alternatively, the request information mayinclude the number of power preference indicator (PPI) signals that werereceived by the eNodeB 112 from the UE 105. In this case, the DRXprofile server 131 may return the updated DRX profile setting (i.e., PPindex value that is unique for each of the respective DRX profiles) tothe eNodeB 112. The eNodeB 112 may forward the updated DRX profilesetting to the UE 105 as confirmation of the change requested by the UE105 from the current DRX profile setting to the updated DRX profilesetting.

FIG. 2 provides a high-level functional block diagram of the PPI managerapplication of a UE 205 and an eNodeB 225. The UE 205 includes a PPImanager application 207, a memory 208, and UE processor and othercomponents 209. The functional components of UE 205 will be described inmore detail with reference to FIG. 5. The PPI manager application 207executes on the UE processor 209 and monitors the operating state of theUE 205. The operating state of the UE 205 may be determined using datafrom various sources. For example, the PPI manager application 207 mayuse information, such as the number of applications operating on the UE211, application information related to the operating applications 213,and data usage information from other sources 219.

Information related the number and types of applications operating onthe UE 205 includes, for example, the number of applications (e.g.,games, stock ticker, news applications, video and audio applications)that a user has selected via an input device to launch, as well asapplications operating in the background, such as global positioningsystem (GPS), Bluetooth, or other applications that may use the datachannel of the UE 205. The number and types of applications operating onthe UE 205 are used by the PPI manager application to assess the use andexpected future use of the data channel by each of the respectiveoperating applications. The application information 213 refers toinformation related to the operating applications, and includes, forexample, an application's tolerance for data delays (e.g., 10milliseconds (ms) to 100 ms, or the like), an amount of data that anapplication uses when communicating via the downlink and/or uplink, andthe like. The data usage information from other sources 219 may behistorical data usage information collected for the differentapplications installed on the UE. The data usage information may bestored on the memory 208 of the UE 205. Alternatively, the “othersources” of data usage information may be servers, such as the DRXProfile server (113 of FIG. 1) or an application server (not shown)connected to the wireless access network 102 of FIG. 1.

In general, and as will be described in more detail with reference toFIGS. 3 and 4, the PPI manager application 207 accesses a DRX profiledata structure (described in more detail with reference to FIGS. 3 and4) in memory 208 and, using the data provided, determines the DRXprofile setting that best conserves power for the UE 205. Upon makingthe selection of the DRX profile, the UE 205 transmits one or more PPIsignals to the eNodeB 225 depending upon the selected DRX profile. TheeNodeB 225 receives the PPI signals, which are then provided to aneNodeB PPI management process 220. The eNodeB PPI management process 220responds to the received PPI signals by accessing a data structure(e.g., table) similar to the DRX profile data structure used by the PPImanager application 207. A database, such as PPI database 221, may storeinformation such as a PPI table and the PPI settings for all PPI-capableUE device connected to an eNodeB. The PPI database 221 may be coupled tothe eNodeB 225, a DRX profile server 230, or both. In an alternativeexample, the eNodeB 225 is connected to the DRX profile server 230,which is configured to manage all of the PPI settings (i.e., DRX profilesettings of connected UEs) for the eNodeB 225. In some examples, the DRXprofile server 230 manages the PPI settings for other eNodeBs (notshown).

In an example, the DRX profile server 230 analyzes operatingstatus-related information provided by the respective connected UEs,such as UE 205, to determine whether additional discontinuous receptionprofiles should be developed or whether present discontinuous receptionprofiles are out-of-date. In response to the analyzing, the DRX profileserver 230 either generates a new DRX profile for inclusion in a revisedDRX profile table (i.e., revised PPI table) or deletes out-of-date DRXprofiles to form a DRX profile table (i.e., revised PPI table).

Based on the received PPI signals and the DRX profile located in the PPItable by the eNodeB PPI management process 220, the eNodeB 225 returnsto the UE 205 a DRX profile indicator that indicates an updated DRXsetting for the UE 205. After updating the DRX profile setting, the UE205 begins operating according to the updated DRX profile setting. Inother words, the UE 205 does not actually operate according to theupdated DRX profile setting until receiving confirmation at the networklevel (i.e., from the eNodeB 225) that the DRX profile setting of the UE205 has been updated.

In another example, the UE 205 may provide operating status information,such as operating parameters of the applications operating on the UE205, to the eNodeB 225. The eNodeB 225 provides the UE 205 operatingstatus information to the DRX profile server 230. The DRX profile server230 is configured via programming instructions to analyze the UEoperating information. Based on the analysis, the DRX profile server 230determines that there is a need for updated DRX profiles, and generatesan updated DRX profile to optimize the DRX performance (e.g., improvespower conservation and uplink and downlink data transmission) of the UE205. In an example, the DRX profile server 230 indicates directly to theeNodeB 225 that the DRX profile setting of the respective UE 205 shouldbe updated to conserve network resources and power of the UE 205. As aresult, the eNodeB 225 sends an updated DRX profile setting signal(e.g., a radio resource control connection reconfiguration(RRCConnectionReconfiguration) signal) to the UE 205, which changes itsDRX profile setting according to the updated DRX profile setting signalfrom the eNodeB 225.

The operation and functions of the PPI manager application 207, the UE205 and the eNodeB 225 may best be explained with reference to theexample operations illustrated in FIG. 3 with reference to the DRXprofile table of FIG. 4.

FIG. 3 illustrates an example of UE configuration signaling exchangedbetween a user equipment (UE), such as 105 and an eNodeB, such as 112.In the UE configuration signaling exchange 300, a UE 310 and an eNodeB320 are exchanging configuration signals for configuring the UE 310.According to examples of the present disclosure, the UE 310 includes aPPI manager application that is executing on a processor of the UE 310.The PPI manager application monitors the operating state of systems onthe UE 310 (i.e., mobile device) and is configured to determine whetherthe monitored operating state of the UE systems conforms with thecurrent DRX profile setting. For example, the UE 310 processor (notshown in this example) may be configured to execute the PPI managerapplication that will identify open applications and obtain operatingparameters regarding the open applications. Operating parameters mayinclude data latency tolerance (i.e., how long the application can gowithout receiving new data), amount of data the application typicallyreceives and how long it typically takes to receive the data via acellular connection, other resources (e.g., video and/or audio codecs,display device, speaker) used by the application, and the like. The PPImanager application determines, based on the operating state (e.g.,number and type of applications open on the UE, demand for a datachannel over which the UE is connected to the network, and the like) ofwhether the operating state of the UE 310 conforms to the current DRXsetting, and based on a result of the determination, outputs a signal.In addition, the UE 310 and the eNodeB 320 may be configured to operateaccording to a number of different DRX profiles. The different DRXprofiles allow the UE 310 to function in different states based on theoperating conditions of the UE 310 at the time. For example, as will bediscussed in more detail below, a change from one DRX profile to anotherDRX profile of the UE 310 may be based on the systems (e.g., processorperformance, display performance, speaker performance and the like)operating on the UE 310.

The eNodeB 320 may determine that the UE 310 connected to the eNodeB 320is a PPI-capable UE. PPI-capable meaning the UE is equipped with a PPImanagement application. This determination may be made for example basedon transmissions by the UE 310 capabilities during the establishment ofa session with the eNodeB 320. In response to the determination, theeNodeB 320 transmits a RRC connection reconfiguration signal. Theinitial setting 307 is a RRC connection reconfiguration signal thatenables use of the Power Preference Indication (PPI) protocol to be usedby the UE 310 during RRC connection mode with the eNodeB 320.

While in the RRC connected mode and with the PPI DRX profile settingenabled, the UE 310 may initiate a voice-over-LTE (VoLTE) call (317). Inresponse to the initiation of the VoLTE call, the eNodeB 320 responds byinforming or instructing the UE 310 of the VoLTE connected-modediscontinuous reception (DRX) default setting via a return message 327.For example, the VoLTE DRX default setting may be 10 milliseconds (ms).The default VoLTE DRX setting may indicate to the UE 310 that after 10ms of inactivity, the UE 310 transitions from an active state to a lowerpower state. The UE 310 may operate at this default VoLTE DRX settingfor a period of time. At some time, the state of the UE 310 changes (forexample, an idling timer times out (i.e., the UE is not very active)) at311. A PPI manager application on the UE 310 that is monitoring theoperating state of the system on the UE 310 may detect this state changeand evaluate the operating state of the UE 310. In an example, the PPImanager application continuously monitors the operating state of thesystem on the UE 310. In another example, the PPI manager applicationmonitors the operating state of the system on the UE 310 periodically(e.g., 5-100 seconds, 1-5 minutes, or the like) in which the periodchanges based on the system operating state or some other condition(e.g., time of day, number of open applications, etc.) of the UE 310. Inresponse to the change of state and the results of the evaluation, theUE 310 transmits, or sends, a DRX setting request message containinginformation related to the DRX setting, or profile of the UE 310 (337).For example, the request message may include a number of single-bit PPIsignals having the same single-bit value corresponding to a lower powerprofile that is selected by the PPI manager from a discontinuousreception profile table stored in a memory of the UE 310. In an example,the UE 310 sends one or multiple PPI signals to initiate the change ofthe DRX setting to the eNodeB 320. The determination of the number ofPPI signals to send and the bit value is made based on a table of DRXprofiles.

A table or file containing the same information, such as that shown inFIG. 4 is stored in both the UE 310 and the eNodeB 320. For example, asshown in FIG. 4, nine (9) DRX profiles (each uniquely identified by oneof PP Index values 1-9) are available. Of course, although nine (9) DRXprofiles are shown, any number of DRX profiles greater than two DRXprofiles may be available for selection. The greater number of profilesallows for greater flexibility with the network throughput andidentifying opportunities to conserve UE battery life. The differentprofiles are based on compromises made for each type of application thatmay be operating on the mobile device. For example, a first applicationmay have a data delay tolerance that overlaps at the higher end of thetolerance with a second application that has a shorter data delaytolerance. As a result, in a DRX profile generated to accommodate boththe first and second applications, such as DRX profile PP Index 5 (SeeFIG. 4), the first application may always have to wait longer (i.e.,farther (or higher)) into its data delay tolerance when the DRX profilePP Index 5 is used. However, with more profiles, less compromises needto be made. For example, a third application's data delay tolerance mayalso overlap with the first application's data delay tolerance, butcloser to the lower end of the tolerance. In a DRX profile generated toaccommodate the first and the third applications, such as DRX profile PPIndex 6, the first application would not have to wait as long toretrieve data when the DRX profile PP Index 6 is used. The generation ofthe different DRX profiles is driven by a specific application's orcombinations of applications that influence on the data channel (and theapplications ability to tolerate data delay), such as the application'sneed for the data channel and/or how frequently the application accessesthe data channel from an idle mode.

In another example, the maximum data delay tolerance of a group ofapplications may vary based on the types of applications (e.g., a stockticker application versus a contact organizer application) in the group.For example, two applications may have vastly different delay tolerances(e.g., App A (e.g., stock ticker) has a lower delay tolerance than App B(e.g., contact organizer). Since App A will be adversely impacted byhaving to wait longer for data, the delay tolerance of App A is morecritical, and is used in the development of the DRX profile for App Aand App B. As a result, the App A and App B DRX profile will not provideas much power savings as a DRX profile developed using only the App Bdata delay tolerance. Of course, if the data delay of App A and App Bwere more similar, more power savings would be achieved. A benefit ofthe presently disclosed examples is that DRX profiles may be developedwith more flexibility that allows for more dynamic and fine graincontrol of the power usage through DRX profiles as opposed to the fairlystatic DRX profile settings described in the Background.

To assist with the determination of which DRX profile is mostappropriate for a UE at any particular time, a Power PreferenceIndicator (PPI) Manager (discussed briefly with reference to FIG. 2) isprovided. In more detail, the PPI manager is an application executing inthe background when the UE is turned “ON.” The PPI manager, for example,uses key applications (e.g., those most frequently used or consideredmost critical to providing an expected quality of service (QoS) for therespective connection) as the basis for determining the particular DRXprofile for the UE. As mentioned above, the PPI Manager determines, forexample, by accessing information from the UE memory about theapplication, or receiving from the application, a maximum data delay anapplication is able to tolerate. For example, in a voice application,the delay cannot be too long—otherwise, data packets may be dropped.Therefore, a DRX profile with a shorter data delay may be selected.Applications may provide to the PPI manager information regarding theapplication's data usage. For example, the applications can sendparameters regarding delay tolerance, performance expected, data rateusage and the like to the PPI manager. In some examples, the PPI managerapplication collects information such as delay, bit rate, jitter delaytolerance, tolerance for lost packets and retransmission, bufferingdelay, and the like as well as QoS parameters, such as, for example,error rates, throughput, bandwidth, transmission delay, jitter and thelike by monitoring the application while the application is executing onthe UE.

FIG. 4 illustrates an example of the information that may be included inthe DRX profile data structure. For example, information such as theProfile Type, an inactivity timer setting, sleep timer setting, powerpreference index, and the like may be stored in the data structure. Theprofile type may be a general description of the operating condition ofthe UE that the profile is attempting to cover. For example, the profiletypes Data Latency 1, Data Latency 2, Heavy Data and Early morning 1Weekday (WKDY) may be used to address applications that are sensitive todelays in receiving data from the network, or scenarios in which datadelays are unwanted. As a result, the inactivity timer and the sleeptimer settings may be set to allow for more frequent reception of dataand for longer durations between idle periods. Conversely, other profiletypes may include settings aimed at conserving power, such as Low Power1, Low Power 2, Late night or Early morning 2 Weekend (WKEND), and maynot be as concerned with receiving data in an expeditious manner. Thedemand for the data channel by the applications running on the mobiledevice is a common criteria of a profile that is included in the morethan two DRX profiles maintained in the data structure. The powerpreference (PP) index is a value that uniquely identifies each of therespective profiles in the DRX profile data structure. For example,profile type Data Latency 1 has a PP Index of 1, while Data Latency 2has a PP Index of 4.

Different applications' usage scenarios cause different problems for themaintenance of the UE 210 battery life. For example, data packets for aVoLTE call, which is performed by a voice application, are short induration and are periodic. As such, when on the VoLTE call, the UE wakesup to perform voice encoding and decoding, and goes back to sleep duringlulls in the conversation. Meanwhile, for video streaming, the usagescenario is different because the UE will be receiving a large amount ofdata, be decoding data more often, and will also be rendering video. Theprevious two examples may be the extremes for data usage, while a moresporadic use of the data channel is web browsing. When web browsing, theweb browser receives a large amount of data in a short amount of time,decodes the data and renders the data (i.e., data channel usage is highand UE system usage is power intensive); however, afterwards, the useris reading the rendered data and the data channel usage is minimal, andUE system power usage is also reduced.

At a high level, the DRX profile types are based on an application'scharacteristics related to data channel usage. For example, a PPImanager may make determinations regarding individual applications orwhether the data channel usage is periodic or aperiodic; whether datausage is low, medium or high; the identified data tolerances for therespective applications; and the like. But battery life is alsocritical; the profiles are generated to be as efficient in the usage ofpower as possible. For example, it is not efficient for the UE to be inan active mode and have no data to send, or to be sleeping (e.g., inidle mode) when there is data waiting to be sent. The different DRXprofiles are based on reaching a balance of the current (i.e., when thePPI manager application is monitoring) operating conditions, inparticular, the power consumption and the data channel usage, of therespective UE. For example, the PPI manager application analyzes thecollected information and determines a DRX profile most suited to thecurrent operating conditions of the UE.

In an alternative example, the PPI manager application may deliverapplication information and information (e.g., via a short messagingservice (SMS) message or other messaging program) related to the UEoperating conditions to a server, such as a DRX profile server 113 ofFIG. 1, via an eNodeB. For example, the DRX profile server 113 may becoupled to the eNodeB 112, and receive the information from the eNodeB112. The DRX profile server 113 may analyze the information provided bythe UE. In response to the analysis, the DRX profile server 113 mayrecommend to (or command) the eNodeB and the UE to switch to a DRXprofile most suited to the current operating conditions of the UE.

Returning to the example of FIG. 3, since a VoLTE call is initiated at317 in the example of FIG. 3, the eNodeB 320 returns to the UE 310, at327, a VoLTE Default profile as the DRX setting for the connectionbetween the UE 310 and eNodeB 320. From Table 1 of FIG. 4, the VoLTEDefault setting has a power preference (PP) index value of 2. Both theUE 310 and the eNodeB 320 may store the PP index value in a memorylocation. The PPI manager analyzes the UE change in state at 312. Forexample, the change in UE state (i.e., UE state change 1) may be a UEidling timeout that is simply an indication that the UE 310 is not verybusy. In response to the analysis, the PPI manager may recommend achange from the present VoLTE default profile to a different DRXprofile, such as a lower power profile. Said differently, the PPImanager adapts the DRX profile setting to the operating state of the UE.By accessing the information in Table 1 of FIG. 4 that is stored, forexample, in the UE 310 memory, the PPI manager, based on the results ofthe analysis, selects a lower power DRX profile. Upon selection of theappropriate DRX profile, the PPI manager identifies using the Table 1information the PP index value of the selected DRX profile.

Based on the selected DRX profile and the current DRX profile, the PPImanager may determine the number and bit value of PPI signals that theUE 310 has to generate and have delivered to the eNodeB 320 in order tochange from the current DRX profile setting to the selected DRX setting.

For example, the current DRX profile is VoLTE default, which is shown inTable 1 with a PP index 2. The selected DRX profile (recall from above,a lower power profile) is, for example, profile type Low Power 2 thathas a PP index value of 5. In this example, the PPI manager determinesthe number of PPI signals to generate and deliver by determining thesigned difference of selected DRX profile PP index value from thecurrent DRX Profile PP index value (i.e., current DRX profile PP indexvalue minus (−) selected DRX profile PP index value), which in theexample is 2−5=−3. So in this example, the number of PPI signals to begenerated to switch to the Low Power 2 DRX profile is 3, and the sign(i.e., (−) or +) indicates the direction in the table to go (i.e. up ordown). The up/down directions are assigned a bit value. For example, thebit value 0 may be assigned the down direction, and the bit value 1 isassigned the up direction. The direction is based on the organization ofthe information in the table, in particular, the PP index values. Forexample, at time of set up or implementation, the agreed uponarrangement of the PP index values is either ascending (i.e., 1 at thetop down to N, where N is an integer) or descending order (i.e. N at thetop down to 1).

Returning to the example, the determined convention at implementation isascending order for PP index values, and negative (i.e., (−)) is downand positive (i.e., +) is up). As discussed above, the number of PPIsignals is 3 and the direction is (−). In the present example, anegative sign indicates downward and the bit value zero (0) is thedownward direction bit value. As a result, as shown in FIG. 3, the PPIsignals output by the UE 310 are three (3) successive, zero (0) bitsignals. The time between outputting the three successive PPI signalsonly has to be as long as needed for the eNodeB 320 to receive andprocess the PPI signal. The time period permits the eNodeB 320 todetermine when a last PPI signal is received. For example, a suitableinterval between PPI signals may be between 1-5 ms, 5-10 ms, 10-30 ms,15-20 ms, 1-100 ms or the like. In some examples, the interval is alsodependent upon the present DRX setting under which the UE and eNodeB areexchanging signals. The eNodeB 320 receives a first PPI signal from theUE 310 and processes (i.e. determines the bit value) the signal, andwaits a predetermined time period for any successive PPI signals fromthe UE 310. After a time, but within the predetermined time period forthe delivery of the PPI signals, the eNodeB 320 receives the three PPIsignals transmitted by the UE 310 to make the change from the currentDRX profile to the selected DRX profile in the example. In an example,the time period (i.e. suitable interval) may be determined according toanalysis of historical data related to the respective DRX profiles.Based on the analysis, the time periods are set or changed, for example,via the PPI manager application 207 in the EU 205 or via the eNodeB PPIManagement 220 in the eNodeB 225 of FIG. 2.

The eNodeB 320 determines the number of PPI signals, for example, bymaintaining a counter for PPI signals from the UE 310. The eNodeB 320determines the direction to traverse a data table stored in memorydepending upon the direction assigned to the respective bit value. Inthis case, the bit value is 0, and the direction is downward in thetable. As shown in FIG. 3, in response to the three successive 0 bitvalued PPI signals, the eNodeB 310 iterates through Table 1 from thecurrent DRX profile setting (i.e., Default VoLTE (PP Index 2)) to theselected DRX profile setting (i.e., Low Power 2 (PP Index 5)). Uponlocating the selected DRX profile setting, the eNodeB 320 adjusts itsDRX setting with respect to the UE 310, and returns a message, such asmessage 347. The message, at 347, indicates to the UE 310 that theeNodeB 320 has confirmed the change from the current DRX profile settingto the selected DRX profile setting.

The UE 310 and eNodeB 320 may operate at the selected DRX profilesetting for a time, which may be a predetermined time, or until acertain time arrives (e.g., midnight or some set time in a preferencesfile of the UE 310), or until a certain event occurs, such as a changein state of the UE 310. For example, at 313, the UE 310 screen turns ON.The UE 310 processor via the PPI manager application analyzes the changein UE state. Based on the PPI manager applications analysis of the UE310 state, the PPI manager recommends a change from the present DRXprofile (i.e., Low Power 2 (PP Index 5)). Based on an analysis of thepresent operating conditions of the UE 310 at 313, the PPI manager mayrecommend a change to a lower delay DRX profile. Based on the analysisand a review of criteria for the respective DRX profile types, the PPImanager recommends, in this example, a change to Data Latency 1, whichis a lower delay DRC profile. Returning to Table 1 in FIG. 3, the DataLatency DRX profile has a PP Index value of 1. Using the abovemethodology for calculating the number and bit value (i.e., directionindicator) of the difference of the (new) selected DRX profile (i.e.,Data Latency 1) from the (previous) selected DRX profile (i.e., LowPower 2), the PPI manager determines the number and bit value for thePPI signals to be sent to the eNodeB 320. For example, the Lower Power 2PP index value is 5 and the Data Latency 1 PP index value is 1. Usingthe signed difference calculation, 5 minus 1 is positive (+) 4. As aresult, the PPI manager instructs the UE 310 processor to output four(4) successive PPI signals with a single bit value of 1 to the eNodeB320 (357). Of course, the four successive PPI signals will be outputafter a predetermined time period to allow for receipt and/or processingof the respective PPI signals by the eNodeB 320. The eNodeB 320 receivesthe four successive, single bit (1) value PPI signals, and, usinginformation from Table 1 of FIG. 3 determines that the new selected DRXprofile is Data Latency 1. The eNodeB 320 returns, at 367, aconfirmation that the DRX profile setting is to be changed to the DataLatency 1 profile type that has a PP Index value of 1. In response tothe confirmation signal (367), the UE 310 changes its DRX profilesettings to the Data Latency 1 DRX profile type.

After operating for some time at the Data Latency 1 DRX profile setting,the PPI manager detects another change is state of the UE 310, andanalyzes the current operational state of the UE 310. At UE state change3 (315), the PPI manager determines that a heavy traffic application isbeing used on the UE 310. In other words, the UE 310 is more activelydownloading data. As a result of the UE state change, the PPI manageraccesses the table of DRX profiles, and locates a DRX profile having thecriteria most closely matching the analyzed operational state of the UE310. For example with reference to Table 1 of FIG. 3, the PPI managerdetermines that the operational state of the UE 310 most closely matchesthe criteria of the Heavy Data profile type, which has a PP index valueof 6. Recall that the present DRX profile type setting between the UE310 and the eNodeB 320 is Data Latency 1, which has a PP index valueof 1. The PPI manager performs the signed difference calculation, whichreturns a difference of 5 and a sign of negative (−). As a result, thePPI manager instructs the UE 310 processor to output five successive,zero bit value PPI signals (377) with the appropriate time periodbetween successive signals. In response to receiving the fivesuccessive, zero bit value PPI signals in the appropriate interval, theeNodeB 320 processes the PPI signals and confirms (387) the change tothe Heavy Data DRX profile type.

Although not shown, the UE 310 in response to the DRX profileconfirmation signals (i.e., signals 327, 347, 367 and 387) may send anacknowledgement back to the eNodeB 320 indicating that the confirmationsignals correctly identify the DRX profile type indicated by the PPImanager. During initialization, UE and Network will reset DRX state to acommon DRX state.

The described examples allow for the generation of multiple DRX profilesbeyond the two profiles presented in the 3GPP, Release 11 document. Forexample, in situations where throughput is diminished, currentimplementations are unable to adjust dynamically to the change inconditions because the DRX profiles needed to adjust are not available.In a concrete example, when a UE is participating in a VoLTE call andperforms a web search, the current DRX settings have difficulty managingthe device to provide optimum performance and efficient power savings.Recall that DRX is intended to be a power saving mechanism for the UE.As a result, a number of DRX profiles may be generated to allow foroptimum device performance as well as increased power savings.

As another example, consider the following with reference to PP Indexvalues 1-3 of Table 1 in FIG. 4. Note each of PP Index values 1-3 has anasterisk adjacent to it and that the table has a footnote stating,“where * indicates an example of most frequently used profiles.” Theinformation in Table 1 may be organized so that the most frequently usedDRX profiles are closest to one another. In this way, a minimum numberof PPI signals, at best, one (1), regardless of bit value need to beexchanged. For example, if Default VoLTE is the most frequently used DRXprofile type, which means the use of the UE 310 most frequently matchesthe criteria of the Default VoLTE profile type, then it may be set at apoint in Table 1 that is central to the next most frequently used DRXprofile, such as Data Latency 1 or Low Power 1. As a result, the PPImanager and the UE 310 processor only have to output one PPI signal witheither a 0 or 1 value, and not multiple signals.

In an example to further minimize wait time for the DRX profile change,a time interval, or time period, length indicator (e.g., 1 or 2 bits) isprovided with the PPI signal (e.g., affixed to the PPI signal or in aseparate control signal) to the respective eNodeB 320, and the eNodeB320 will have a time interval setting that corresponds to the indicatedtime interval (i.e., time period) length. In such an example, the eNodeB320 processes the PPI signal as usual except according to the indicatedtime interval length.

In some examples, the information in Table 1 may be a dynamic. Forexample, the PPI manager may reorganize the DRX profile types within theTable 1 by reassigning PP Index values to DRX profiles that aredetermined to be more frequently used, or used less frequently, and as aresult, to more efficiently traverse the table, the PPI managerreassigns the DRX profile type PP Index values. Of course, thisreassigned DRX profile type PP Index values are shared with therespective eNodeB 320 with which the UE 310 communicates. Alternatively,the eNodeB 320 may use network resources, such as DRX setting server113, to perform the dynamic analysis of the DRX profile table. Uponconclusion of the analysis, the eNodeB 320 may download the DRX profiletable to a specific UE or to all PPI capable UEs connected to the eNodeB320. The eNodeB 320 may confirm the table version stored on each UE atthe time of establishing a session with the respective UE.

In another example of the PPI message sent at 337 of FIG. 3, the PPIvalue may be more than a single bit. For example, a number of bits thatspecify a value that corresponds to a particular DRX setting or profilemay be transmitted. In this example, the PPI message sent by the UE mayinclude a PPI value based on multiple bits corresponding to a lowerpower profile that is selected by the PPI manager from a discontinuousreception profile table stored in a memory of the UE 310. In addition orin another example, a multi-bit PPI value includes a first bitindicating up or down direction in the table, and the next predeterminedn bits indicate, in binary the number of steps (e.g., 3 steps=11 (inbinary)). This allows a greater number of combinations with fewer bitsfor more states (e.g., 16 states=5 bits, vs. having to send out 7 bitsfor a max shift). Furthermore, time is saved as there is less wait timefor additional PPI signals and the opportunity for errors is reduced.

Regarding possible errors, an example is envisioned in which the eNodeB320 is configured to distinguish between expected values and receivedvalues, and response performing error correction. For example, in anearlier example, a PPI signal output by the UE 310 are a negative signindicator, which indicates a downward direction in the discontinuousprofile table, and three (3) successive, zero (0) bit signals (i.e., 0,0, 0), which represent the number of steps within the discontinuousprofile table. Suppose that due to an issue in the communication channelthat middle signal of the three successive signals indicates a one (1)instead of a zero (0) (i.e., 0, 1, 0). Since the eNodeB 320 wasexpecting successive signals with zero bits, the eNodeB 320, in thisexample, is configured to note the different PPI signal value. Inresponse to noting the difference between the successive signals, theeNodeB 320 requests a re-transmission of the erroneous PPI signal.Alternatively, the eNodeB 320 based on the values of the other receivedPPI signals in the succession of PPI signals determines that the valueof the particular PPI signal is an error, and simply changes the valueto conform with the other PPI signal values. Returning to the example ofsuccessive PPI signals (i.e., 0, 1, 0), in which the middle PPI signalvalue is a one (1) instead of a zero (0), the eNodeB 320 identifies thepotential error, and based on the bit values of the PPI signals receivedprior to and afterwards, determines that the value of middle PPI signalshould have been a zero (0). In response to the determination, theeNodeB 320 counts the middle PPI signal as another successive zerosignal. In other words, the minority PPI signal value is replaced withthe majority PPI signal value. Accordingly, the eNodeB 320 traverses thediscontinuous profile table for three successive zero (0) steps. Ofcourse, other error correction methodologies may be implemented thataccomplish a similar result.

At this time, it may be useful to consider, at a high level, thefunctional elements/aspects of the UE 310 and the PPI manager in moredetail. FIG. 5 provides a block diagram illustration of an example oftouch-screen type mobile device 13. A UE, such as mobile device 13,although shown as a handheld smartphone for discussion purposes, mayalso be a tablet or may be incorporated into another device, such as apersonal digital assistant (PDA) or the like. The mobile device 13functions as a normal digital wireless telephone device. For thatfunction, the device 13 includes a microphone 1002 for audio signalinput and a speaker 1004 for audio signal output. The microphone 1002and speaker 1004 connect to voice coding and decoding circuitry(vocoder) 1006. For a voice telephone call, for example, the vocoder1006 provides two-way conversion between analog audio signalsrepresenting speech or other audio and digital samples at a compressedbit rate compatible with the digital protocol of wireless telephonenetwork communications or voice over packet (Internet Protocol)communications.

For digital wireless communications, the handset 13 also includes atleast one digital transceiver (XCVR) 1008. Today, the handset 13 isconfigured for digital wireless communications using one or more of thecommon network technology types. In an example, the XCVR 1008 isconfigured as a transceiver suitable data (which includes voice)communications over a long term evolution (LTE) network according to anystandards or requirements related to VoLTE. The concepts discussed hereencompass embodiments of the mobile device 13 utilizing any digitaltransceivers that conform to current or future developed digitalwireless communication standards. The mobile device 13 may also becapable of analog operation via a legacy network technology.

The transceiver 1008 provides two-way wireless communication ofinformation, such as vocoded speech samples and/or digital informationfor data communications (including for authentication), in accordancewith the technology of the networks of FIG. 1. The transceiver 1008 alsosends and receives a variety of signaling messages in support of thevarious voice and data services provided via the mobile device 13 andthe communication network. Each transceiver 1008 connects through RFsend and receive amplifiers (not separately shown) to an antenna 1009.

A microprocessor 1062 serves as a programmable controller for the mobiledevice 13, in that it controls all operations of the mobile device 13 inaccord with programming that it executes, for all normal operations, andfor operations involved in the mobile application adaptive DRX profilesetting service under consideration here. A microprocessor, orgenerally, a processor, is a hardware circuit having elements structuredand arranged to perform one or more processing functions, typicallyvarious data processing functions. Although discrete logic componentscould be used, the examples utilize components forming a programmablecentral processing unit (CPU). A microprocessor for example includes oneor more integrated circuit (IC) chips incorporating the electronicelements to perform the functions of the CPU. The microprocessor 1062,for example, may be based on any known or available microprocessorarchitecture, such as a Reduced Instruction Set Computing (RISC) usingan ARM architecture, as commonly used today in mobile devices and otherportable electronic devices. Of course, other microprocessor circuitrymay be used to form the CPU or processor hardware in server computers orother user terminal computer equipment.

The microprocessor 1062 serves as the programmable host for mobiledevice 13 by configuring the mobile device 13 to perform variousoperations, for example, in accordance with instructions or programmingexecutable by microprocessor 1062. For example, such operations mayinclude various general operations of the mobile device 13 as well asoperations related to confirming or adjusting operational settings ofthe mobile device 13, contacting network devices, storing userpreference information, controlling encoding/decoding of voice and videodata, and the like. Although a processor may be configured by use ofhardwired logic, typical processors in mobile devices are generalprocessing circuits configured by execution of programming. Themicroprocessor 1062 connects to other elements of the mobile device 13via appropriate circuitry, such as bus or terminal connections. In apresent example, the mobile device 13 includes flash type program memory1064, for storage of various “software” or “firmware” program routinessuch as device operating system (OS), voice encoding/decodingalgorithms, video encoding/decoding algorithms, programs related tographical user interface elements and functions. The memory 1064 alsostores mobile configuration settings, such as the MDN, the IMEID and/ormobile identification number (MIN), etc. The mobile device 13 may alsoinclude a non-volatile random access memory (RAM) 1033 for a workingdata processing memory. Of course, other storage devices orconfigurations may be added to or substituted for those in the example.The memories 1064, 1033 also store various data, such as telephonenumbers and server addresses, downloaded data such as multimedia contentand applications, and various data input by the user. Programming storedin the flash type program memory 1064, sometimes referred to as“firmware,” is loaded into and executed by the microprocessor 1062. Forexample, the PPI manager application code is stored in the memory 1064.

As outlined above, the mobile device 13 includes a processor, andprogramming, such as mobile application(s) 1030, stored in the memory1064 configures the processor so that the mobile device is capable ofperforming various desired functions, including in this case thefunctions involved in the technique for providing revisions to thediscontinuous reception settings of the mobile device 13. The logicimplemented by the processor 1062 of the mobile device 13 configures theprocessor 1062 to control various functions as implemented by the mobiledevice 13. The logic for a processor 1062 may be implemented in avariety of ways, but in our example, the processor logic is implementedby programming for execution by the processor 1062. Regular operationsof the device are controlled by operation of the processor 1062. DRXtables and applications, such as the PPI manager application, 1300 maybe stored in flash memory 1064. The DRX tables may include a list ofdifferent DRX profiles that are suitable for different use cases of theUE 13. The DRX profiles 1300 stored in memory 1064 may be based on thenumber of applications open on the UE, the data usage requirements foreach open application, data delay tolerances for each application and alevel of user interaction with the device at a given moment. In additionto the different applications (e.g., games, productivity, entertainment(video and/or audio), voice and so on), which are stored in memory 1064,a power management application may also be stored in the memory 1064.

The mobile device 13 includes a touch-screen display 1020 for displayingmessages, menus or the like, call related information dialed by theuser, calling party numbers, etc., including the described adaptive DRXprofile setting service. Keys 1030 or a virtual keyboard presented viathe touch-screen display 1020 may enable dialing digits for voice and/ordata calls as well as generating selection inputs, for example, as maybe keyed-in by the user based on a displayed menu or as a cursor controland selection of a highlighted item on a displayed screen. Thetouch-screen display 1020 and keys 1030 are the physical elementsproviding a textual or graphical user interface. Various combinations ofthe keypad 120, touch-screen display 1020, microphone 1002 and speaker1004 may be used as the physical input output elements of the graphicaluser interface (GUI), for multimedia (e.g., audio and/or video)communications including communications/interactions related to voiceand/or video calling. Of course other user interface elements may beused, such as a trackball, as in some types of PDAs or smart phones.

In addition to normal telephone and data communication relatedinput/output, the user interface elements also may be used for displayof menus and other information to the user and user input of selections,including any needed during user selection of a menu option. Forexample, if used as a selection device, the user interface elementsallow a user to input information or make setting selections via, forexample, interactions with the PPI manager application, related to theuser's usage of the UE and respective data channel for DRX purposes.

For input purposes, touch screen display 1020 includes a plurality oftouch sensors 1022. Other interface elements may include a keypadincluding one or more keys 1030. For example, the keypad may beimplemented in hardware as a T9 or QWERTY keyboard of mobile device 13and keys 1030 may correspond to the physical keys of such a keyboard.Alternatively, keys 1030 (and keyboard) of mobile device 13 may beimplemented as “soft keys” of a virtual keyboard graphically representedin an appropriate arrangement via touch screen display 1020. The softkeys presented on the touch screen display 1020 may allow the user ofmobile device 13 to invoke the same user interface functions as with thephysical hardware keys. In some implementations, the microphone 1002 andspeaker 1004 may be used as additional user interface elements, foraudio input and output, including with respect to some functions relatedto the video calling processing and communication, as described herein.The different user interface elements may be used to navigate throughthe examples of video calling service graphical user interfacesdescribed herein.

For output, touch screen display 1020 is used to present information(e.g., text, video, graphics or other visible digital media content) tothe user of mobile device 13. Processor 1062 controls visible displayoutput on the LCD or other display element of the touch screen display1020 via a display driver 1024, to present the various visible outputsto the device user.

In general, touch screen display 1020 and touch sensors 1022 (and one ormore keys 1030, if included) are used to provide the textual andgraphical user interface for the mobile device 13. In an example, touchscreen display 1020 provides viewable content to the user at mobiledevice 13. Touch screen display 1020 also enables the user to interactdirectly with the viewable content provided in the content display area,typically by touching the surface of the screen with a finger or animplement such as a stylus.

As shown in FIG. 5, the mobile device 13 also includes a sense circuit1028 coupled to touch sensors 1022 for detecting the occurrence andrelative location/position of each touch with respect to a contentdisplay area of touch screen display 1020. In addition, the sensecircuit 1028 is configured to provide processor 1062 with touch-positioninformation based on user input received via touch sensors 1022 (e.g. auser interface element). In some implementations, processor 1062 isconfigured to correlate the touch position information to specificcontent being displayed within the content display area on touch screendisplay 1020. The touch-position information captured by sense circuit1028 and provided to processor 1062 may include, but is not limited to,coordinates identifying the location of each detected touch with respectto the display area of touch screen display 1020 and a timestampcorresponding to each detected touch position.

There are a variety of ways that a mobile device 13 may be configured toobtain information with respect to current location of the device. Inour example, the mobile device 13 includes a global positioningsatellite (GPS) receiver 1032 and associated antenna 1034. Locationinformation, in some examples, may be used by the PPI manager in makingrecommendations regarding the DRX settings.

As known in the data processing and communications arts, ageneral-purpose computer typically comprises a central processor orother processing device, an internal communication bus, various types ofmemory or storage media (RAM, ROM, EEPROM, cache memory, disk drivesetc.) for code and data storage, and one or more network interface cardsor ports for communication purposes. The software functionalitiesinvolve programming, including executable code as well as associatedstored data, e.g. files used for the adaptive DRX profile settingservice examples described herein. The software code is executable bythe general-purpose computer that functions as DRX profile server. Inoperation, the code is stored within the general-purpose computerplatform. At other times, however, the software may be stored at otherlocations and/or transported for loading into the appropriategeneral-purpose computer system. Execution of such code by a processorof the computer platform enables the platform to implement themethodology for selection of DRX profile settings, in essentially themanner performed in the implementations discussed and illustratedherein.

FIG. 6 depicts a system with one or more wireless transceivers, as maybe used to implement a wireless network node, such as eNodeB 112 inFIG. 1. A wireless network node, such as an evolved node B, alsoincludes a data communication interface, CPU, main memory and storagefor data and/or programming (see FIG. 6). In addition, such wirelessnetwork node includes one or more wireless transceivers in order toprovide communications services to one or more mobile devices viavarious radio frequencies in compliance with one or more wirelesscommunications standards (e.g., LTE). Although FIG. 6 depicts the systemenclosed within a single structure, such physical structure is notrequired. Alternatively, or in addition, certain components may belocated, either physically or logically, within disparate elements. Forexample, while the wireless network node includes the data communicationinterface and wireless transceiver(s), processing to control suchcommunication interfaces may be implemented by a CPU and programmingstored in a memory of another device, such as MME 52.

FIG. 7 provides a functional block diagram illustration of a generalpurpose computer hardware platform.

More specifically, FIG. 7 illustrates a network or host computerplatform, as may typically be used to implement a server, such as DRXprofile server and/or any of the other servers/platforms implementingthe enhanced more than two DRX profile setting related functions shownin FIG. 1 or 2. A server, for example, includes a data communicationinterface for packet data communication (see FIG. 7). The server alsoincludes processor hardware implementing a central processing unit(CPU), in the form of one or more processors, for executing programinstructions. The server platform typically includes an internalcommunication bus, program storage, and data storage for various datafiles to be processed and/or communicated by the server, although theserver often receives programming and data via network communications.The hardware elements, operating systems and programming languages ofsuch servers are conventional in nature, and it is presumed that thoseskilled in the art are adequately familiar therewith. Of course, theserver functions may be implemented in a distributed fashion on a numberof similar platforms, to distribute the processing load. The softwareprogramming relating to the VoLTE admission control techniques discussedherein may be downloaded and/or updated from a computer platform, forexample, to configure the eNodeB or other server (e.g. FIG. 1 or 2) orfrom a host computer or the like communicating with the mobile devicevia the network (e.g. FIG. 1 or 2).

Hence, aspects of the methods of selecting a DRX profile or permittingthe change of a DRX profile outlined above may be embodied inprogramming. Program aspects of the technology may be thought of as“products” or “articles of manufacture” typically in the form ofexecutable code and/or associated data that is carried on or embodied ina type of machine readable medium. “Storage” type media include any orall of the tangible memory of the computers, processors or the like, orassociated modules thereof, such as various semiconductor memories, tapedrives, disk drives and the like, which may provide non-transitorystorage at any time for the software programming. All or portions of thesoftware may at times be communicated through the Internet or variousother telecommunication networks. Such communications, for example, mayenable loading of the software from one computer or processor intoanother, for example, from a management server or host computer of thecellular service provider into the computer platform of the wirelessaccess network that may be the DRX profile server 113. Thus, anothertype of media that may bear the software elements includes optical,electrical and electromagnetic waves, such as used across physicalinterfaces between local devices, through wired and optical landlinenetworks and over various air-links. The physical elements that carrysuch waves, such as wired or wireless links, optical links or the like,also may be considered as media bearing the software. As used herein,unless restricted to non-transitory, tangible “storage” media, termssuch as computer or machine “readable medium” refer to any medium thatparticipates in providing instructions to a processor for execution.

Hence, a machine readable medium may take many forms, including but notlimited to, a tangible storage medium, a carrier wave medium or physicaltransmission medium. Non-volatile storage media include, for example,optical or magnetic disks, such as any of the storage devices in anycomputer(s) or the like, such as may be used to implement the servicefor selecting DRX profiles, etc. shown in the drawings. Volatile storagemedia include dynamic memory, such as main memory of such a computerplatform. Tangible transmission media include coaxial cables; copperwire and fiber optics, including the wires that comprise a bus within acomputer system. Carrier-wave transmission media can take the form ofelectric or electromagnetic signals, or acoustic or light waves such asthose generated during radio frequency (RF) and infrared (IR) datacommunications. Common forms of computer-readable media thereforeinclude for example: a floppy disk, a flexible disk, hard disk, magnetictape, any other magnetic medium, a CD-ROM, DVD or DVD-ROM, any otheroptical medium, punch cards paper tape, any other physical storagemedium with patterns of holes, a RAM, a PROM and EPROM, a FLASH-EPROM,any other memory chip or cartridge, a carrier wave transporting data orinstructions, cables or links transporting such a carrier wave, or anyother medium from which a computer can read programming code and/ordata. Many of these forms of computer readable media may be involved incarrying one or more sequences of one or more instructions to aprocessor for execution.

While the foregoing has described what are considered to be the bestmode and/or other examples, it is understood that various modificationsmay be made therein and that the subject matter disclosed herein may beimplemented in various forms and examples, and that the teachings may beapplied in numerous applications, only some of which have been describedherein. It is intended by the following claims to claim any and allapplications, modifications and variations that fall within the truescope of the present teachings.

Unless otherwise stated, all measurements, values, ratings, positions,magnitudes, sizes, and other specifications that are set forth in thisspecification, including in the claims that follow, are approximate, notexact. They are intended to have a reasonable range that is consistentwith the functions to which they relate and with what is customary inthe art to which they pertain.

The scope of protection is limited solely by the claims that now follow.That scope is intended and should be interpreted to be as broad as isconsistent with the ordinary meaning of the language that is used in theclaims when interpreted in light of this specification and theprosecution history that follows and to encompass all structural andfunctional equivalents. Notwithstanding, none of the claims are intendedto embrace subject matter that fails to satisfy the requirement ofSections 101, 102, or 103 of the Patent Act, nor should they beinterpreted in such a way. Any unintended embracement of such subjectmatter is hereby disclaimed.

Except as stated immediately above, nothing that has been stated orillustrated is intended or should be interpreted to cause a dedicationof any component, step, feature, object, benefit, advantage, orequivalent to the public, regardless of whether it is or is not recitedin the claims.

It will be understood that the terms and expressions used herein havethe ordinary meaning as is accorded to such terms and expressions withrespect to their corresponding respective areas of inquiry and studyexcept where specific meanings have otherwise been set forth herein.Relational terms such as first and second and the like may be usedsolely to distinguish one entity or action from another withoutnecessarily requiring or implying any actual such relationship or orderbetween such entities or actions. The terms “comprises,” “comprising,”or any other variation thereof, are intended to cover a non-exclusiveinclusion, such that a process, method, article, or apparatus thatcomprises a list of elements does not include only those elements butmay include other elements not expressly listed or inherent to suchprocess, method, article, or apparatus. An element proceeded by “a” or“an” does not, without further constraints, preclude the existence ofadditional identical elements in the process, method, article, orapparatus that comprises the element.

The Abstract of the Disclosure is provided to allow the reader toquickly ascertain the nature of the technical disclosure. It issubmitted with the understanding that it will not be used to interpretor limit the scope or meaning of the claims. In addition, in theforegoing Detailed Description, it can be seen that various features aregrouped together in various embodiments for the purpose of streamliningthe disclosure. This method of disclosure is not to be interpreted asreflecting an intention that the claimed embodiments require morefeatures than are expressly recited in each claim. Rather, as thefollowing claims reflect, inventive subject matter lies in less than allfeatures of a single disclosed embodiment. Thus the following claims arehereby incorporated into the Detailed Description, with each claimstanding on its own as a separately claimed subject matter.

What is claimed is:
 1. A mobile device, comprising: a radio transceivercommunicatively coupled to a component of a mobile communicationnetwork; a memory storing data related to a state of systems operatingon the mobile device, a table of more than two discontinuous receptionprofiles, and executable program instructions for determining adiscontinuous reception profile for selection from the table; aprocessor connected to control the radio transceiver and to have accessto the memory, wherein the processor when executing the programinstructions is configured to perform functions, including functions to:based on a signal received via the radio transceiver, identify adiscontinuous reception profile from the table of discontinuousreception profiles in the memory, wherein the table includes more thantwo discontinuous reception profiles, each of the more than twodiscontinuous reception profiles uniquely identified by a profilepreference index value and criteria for each of the more than twodiscontinuous reception profiles; configure a discontinuous receptionsetting of the mobile device according to the identified discontinuousreception profile including the power preference index value of theidentified discontinuous reception profile in the discontinuousreception profiles table; monitor the state of systems operating on themobile device; determine whether the monitored state of the systemsoperating on the mobile device conforms with the identifieddiscontinuous reception profile; and transmit through the mobilecommunication network, a signal based on a result of the determination,wherein the outputted signal indicates a change of the discontinuousreception setting of the mobile device to another discontinuousreception profile in the discontinuous reception profiles table.
 2. Themobile device of claim 1, wherein when determining whether the monitoredstate of the systems operating on the mobile device conforms with theidentified discontinuous reception profile, the processor is furtherconfigured to perform functions, including functions to: compare themonitored state of the systems operating on the mobile device with thecriteria for the identified discontinuous reception profile; in responseto a comparison result that indicates a desire to change thediscontinuous reception profile, locate a discontinuous receptionprofile in the table that has criteria that matches the monitored stateof the systems operating on the mobile device; in response to locating amatching discontinuous reception profile in the table, generate a powerpreference signal; and transmit, via the radio transceiver, the powerpreference signal to the component of a mobile communication network asa request to modify a setting of the discontinuous reception profile inthe component of the mobile communication network.
 3. The mobile deviceof claim 2, the processor is further configured to perform functions,including functions to: identify, in the discontinuous reception profiletable, a power preference index associated with the matchingdiscontinuous reception profile; compare the power preference index ofthe identified discontinuous reception profile used to configure thediscontinuous reception setting of the mobile device to the powerpreference index of the matching discontinuous reception profile; andbased on the results of the comparison, determine an index differencevalue between the two power preference indexes in the discontinuousreception profiles table and a direction indicator, wherein thedirection indicator indicates a direction of the matching discontinuousreception profile from the identified discontinuous reception profile inthe discontinuous reception profiles table.
 4. The mobile device ofclaim 3, wherein the generated power preference signal is based on thedirection indicator.
 5. The mobile device of claim 3, wherein the indexdifference value is the difference distance.
 6. The mobile device ofclaim 2, wherein prior to generating the power preference signal, theprocessor is further configured to perform functions, includingfunctions to: determine a direction in the discontinuous receptionprofile table that the matching discontinuous reception is from thediscontinuous reception setting of the mobile device based on a powerpreference index; set a first bit value for the power preference signalbased on the determined direction being upwards in the table or set asecond bit value for the power preference signal based on the determineddirection being downwards in the table; and based on a magnitude of thedifference, determine a number of power preference signals to begenerated.
 7. The mobile device of claim 6, wherein the transmittedpower preference signal is of the set bit value, the processor isfurther configured to perform functions, including functions to: wait apredetermined time period; transmit another power preference signal ofthe same bit value; and repeat the waiting and transmit until the lastof the determined number of power preference signals to be generatedhave been transmitted.
 8. The mobile device of claim 7, wherein theprocessor is further configured to perform functions, includingfunctions to: receive a power preference indication from the componentof the mobile communication network, wherein the power preferenceindication indicates a modification to the discontinuous receptionsetting in the component of the mobile communication network; and inresponse to the received power preference indication from the component,switch the discontinuous reception setting of the mobile device to theindicated power preference.
 9. A mobile communication network component,comprising: a wireless transceiver for exchanging signals from a mobiledevice; a memory storing executable program instructions for setting adiscontinuous reception profile for the mobile device; a processorconnected to have access to the memory, wherein the processor whenexecuting program instructions is configured to perform functions,including functions to: receive multiple power preference indicationsetting signals having the same value within a predetermined timeframefrom the mobile device; in response to receiving the multiple powerpreference indication setting signals, access a table of discontinuousreception profiles; using a current discontinuous reception profilesetting as an entry point of the table, identify an updateddiscontinuous reception profile in the table based on a number of themultiple power preference indication setting signals received within thepredetermined timeframe from the mobile device; and in response tolocating the updated discontinuous reception profile in the table,transmit a signal indicating the updated discontinuous reception profileto the mobile device.
 10. The mobile communication network component ofclaim 9, wherein when identifying an updated discontinuous receptionprofile in the table, the processor is configured by executing programinstructions to perform additional functions, including functions to:maintain a count of individual power preference indication settingsignals received in the multiple power preference indication settingsignals; after the predetermined timeframe and based on the count,identify the number of power preference indication setting signalsreceived; identify a bit value of the individual power preferenceindication setting signals received in the multiple power preferenceindication setting signals, wherein the identified bit value indicates adirection in the discontinuous reception profile table to move toperform the identification of the discontinuous reception profile;traverse the table of discontinuous reception profiles, starting fromthe current discontinuous reception profile setting, for the identifiednumber of received power preference indication setting signals and inthe direction indicated by the identified bit value; and upon completionof the traversal of the table, identify the updated discontinuousreception profile.
 11. The mobile communication network component ofclaim 9, wherein the processor when executing program instructions isconfigured to perform additional functions, including functions to:receive information related to the operational status of the mobiledevice; analyze the information to determine whether additionaldiscontinuous reception profiles should be developed or presentdiscontinuous reception profiles are out-of-date; in response to theanalyzing, either generate a new discontinuous reception profile forinclusion in or delete out-of-date discontinuous reception profiles toform a revised discontinuous reception profile table; and deliver therevised discontinuous reception profile table to the mobile device. 12.The mobile communication network component of claim 9, furthercomprising: a connection to a discontinuous reception profile settingserver, wherein the processor when executing program instructions isconfigured to perform additional functions, including functions to:receive information related to the operational status of the mobiledevice; provide the information to the discontinuous reception profilesetting server; after providing the information, receive a reviseddiscontinuous reception profile table from the discontinuous receptionprofile setting server, wherein the revised discontinuous receptionprofile table includes additional profiles or a reduced number ofprofiles; and deliver the revised discontinuous reception profile tableto the mobile device.
 13. A method, comprising: identifying adiscontinuous reception profile from a table of discontinuous receptionprofiles in a memory, wherein the table includes more than twodiscontinuous reception profiles, each of the more than twodiscontinuous reception profiles uniquely identified by a profilepreference index value and criteria for each of the more than twodiscontinuous reception profiles; configuring a discontinuous receptionsetting of a mobile device according to the identified discontinuousreception profile, including the power preference index value of theidentified discontinuous reception profile in the discontinuousreception profiles table stored in the memory; monitoring the state ofsystems operating on the mobile device; determining whether themonitored state of the systems operating on the mobile device conformswith the identified discontinuous reception profile; and based on aresult of the determination, transmitting through the mobilecommunication network, wherein the transmitted signal indicates a changeof the discontinuous reception setting of the mobile device to anotherdiscontinuous reception profile in the discontinuous reception profilestable.
 14. The method of claim 13, wherein when determining whether themonitored state of the systems operating on the mobile device conformswith the identified discontinuous reception profile, comprises:comparing the monitored state of the systems operating on the mobiledevice with criteria for the identified discontinuous reception profile;in response to a comparison result that indicates a desire to change thediscontinuous reception profile, locating a discontinuous receptionprofile in the table that has criteria that matches the monitored stateof the systems operating on the mobile device; in response to locating amatching discontinuous reception profile in the table, generating apower preference signal; and transmitting, via a radio transceiver, thepower preference signal to the component of a mobile communicationnetwork as a request to modify a setting of the discontinuous receptionprofile in the component of the mobile communication network.
 15. Themethod of claim 14, wherein the generated power preference signal isbased on the direction indicator.
 16. The method of claim 14, furthercomprising: prior to generating the power preference signal, determininga direction in the discontinuous reception profile table that thematching discontinuous reception is from the discontinuous receptionsetting of the mobile device based on a power preference index; settinga first bit value for the power preference signal based on thedetermined direction being upwards in the table or set a second bitvalue for the power preference signal based on the determined directionbeing downwards in the table; and based on a magnitude of thedifference, determining a number of power preference signals to begenerated.
 17. The method of claim 14, further comprising: sendinginformation related to an operating state of applications operating onthe mobile device to a mobile communication network entity; receivingfrom the mobile communication network entity, an updated discontinuousreception profile table; and replacing the discontinuous receptionprofile table with the updated discontinuous reception profile table.18. The method of claim 14, further comprising: identifying, in thediscontinuous reception profile table, a power preference indexassociated with the matching discontinuous reception profile; comparingthe power preference index of the identified discontinuous receptionprofile used to configure the discontinuous reception setting of themobile device to the power preference index of the matchingdiscontinuous reception profile; and based on the results of thecomparison, determining an index difference value between the two powerpreference indexes in the discontinuous reception profiles table and adirection indicator, wherein the direction indicator indicates adirection of the matching discontinuous reception profile from theidentified discontinuous reception profile in the discontinuousreception profiles table.
 19. The method of claim 16, wherein the indexdifference value is the difference distance.